Skip to content

feat: add spectracleanse-engineering Claude plugin (9 skills, 2 agents, 6 docs)#42

Merged
ChrisAdamsdevelopment merged 1 commit into
mainfrom
feat/spectracleanse-engineering-claude-plugin
May 24, 2026
Merged

feat: add spectracleanse-engineering Claude plugin (9 skills, 2 agents, 6 docs)#42
ChrisAdamsdevelopment merged 1 commit into
mainfrom
feat/spectracleanse-engineering-claude-plugin

Conversation

@ChrisAdamsdevelopment
Copy link
Copy Markdown
Owner

@ChrisAdamsdevelopment ChrisAdamsdevelopment commented May 24, 2026

Purpose-built Claude plugin for SpectraCleanse engineering — covers code review, deploy readiness, auth/billing debugging, media pipeline safety, incident response, and founder operating review. All content verified from the actual repo.

Summary

  • Adds the spectracleanse-engineering Claude plugin.
  • Includes 9 engineering skills.
  • Includes 2 focused agents.
  • Includes 6 supporting docs.
  • Covers code review, deploy readiness, auth/billing debugging, media pipeline safety, incident response, and founder operating review.

Verification

  • Plugin content was checked against the actual SpectraCleanseAI repo.

Summary by Sourcery

Add a dedicated SpectraCleanse engineering Claude plugin with repo-specific skills, agents, and documentation to support development, deployment, operations, and review workflows.

New Features:

  • Introduce the spectracleanse-engineering Claude plugin providing SpectraCleanse-specific engineering assistance across code review, deployment, auth/billing, processing, incidents, documentation, testing strategy, and founder operating reviews.
  • Add two specialized agents for repository research and production incident command within the SpectraCleanse context.

Enhancements:

  • Document SpectraCleanse’s architecture, stack, environment variables, deployment model, supported formats, and product context for use by the plugin and engineering team.
  • Provide detailed deploy checklists, MCP integration roadmap, and plugin validation guides to standardize operational and validation workflows.
  • Add a changelog to track evolution of the spectracleanse-engineering plugin.

@vercel
Copy link
Copy Markdown

vercel Bot commented May 24, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
spectracleanseai Ready Ready Preview, Comment, Open in v0 May 24, 2026 1:56pm

@sourcery-ai
Copy link
Copy Markdown

sourcery-ai Bot commented May 24, 2026

Reviewer's Guide

Adds a purpose-built spectracleanse-engineering Claude plugin for the SpectraCleanse repo, including engineering-focused skills, agents, and docs for code review, deploy readiness, processing pipeline safety, auth/billing debugging, incident response, documentation accuracy, testing strategy, and founder operating reviews, plus installation/validation and MCP/deploy/env/format references.

File-Level Changes

Change Details Files
Introduce SpectraCleanse-specific engineering docs for plugin validation, product context, env/secrets, Render/Hyperlift deploys, MCP roadmap, and supported formats.
  • Document how to install and validate the spectracleanse-engineering plugin locally, plus manual skill-level validation steps.
  • Capture product and stack facts (APIs, plans, formats, risks, discrepancies) in a central product-context reference.
  • Provide an env and secrets reference mapping all backend/frontend env vars, their requiredness, and Render-specific notes.
  • Add a Render/Hyperlift deploy checklist with Node version, build, env, CORS, DB persistence, Stripe, and smoke-test gates.
  • Define an MCP integration roadmap and security guidance for Admin MCP, GitHub, Sentry, and Playwright servers.
  • Document supported formats and processing boundaries based on cleansePolicy, Multer MIME list, and processor behavior.
spectracleanse-engineering/docs/plugin-validation.md
spectracleanse-engineering/docs/product-context.md
spectracleanse-engineering/docs/env-and-secrets-reference.md
spectracleanse-engineering/docs/render-deploy-checklist.md
spectracleanse-engineering/docs/mcp-roadmap.md
spectracleanse-engineering/docs/supported-formats-and-processing-boundaries.md
Add SpectraCleanse-focused Claude skills that encode architecture, code review, deploy readiness, processing pipeline, auth/billing, incident response, documentation standards, testing strategy, and founder operating review workflows.
  • Create a code-review skill with checklists around upload handling, ExifTool usage, Gemini parsing, JWT/Stripe/CORS, and frontend integration.
  • Define an architecture skill describing the current monolith, SQLite, ExifTool, deployment constraints, and decision frameworks for splitting services, storage, queues, and auth expansion.
  • Provide a deploy-readiness skill that turns repo facts into a conservative pre-deploy checklist and smoke tests for Render/Hyperlift.
  • Encode the processing pipeline skill with detailed mode descriptions (Quick Cleanse vs Full Server Cleanse vs batch vs SEO), metadata rules, trust boundaries, and failure modes.
  • Add an auth/billing skill detailing JWT flows, plan enforcement, Stripe checkout/webhook behavior, and debugging steps for desynced plans or 402s.
  • Add an incident-response skill that classifies common SpectraCleanse incidents and prescribes triage steps and output format.
  • Add a documentation skill to keep README/env/API/format docs aligned with code, including known discrepancies and rules not to overclaim support.
  • Add a testing-strategy skill that audits the current lack of tests and proposes phased smoke, unit, integration, and E2E coverage.
  • Add a founder-operating-review skill to structure solo-founder reviews around shipped work, risks, friction, and next actions.
spectracleanse-engineering/skills/spectracleanse-code-review/SKILL.md
spectracleanse-engineering/skills/spectracleanse-architecture/SKILL.md
spectracleanse-engineering/skills/spectracleanse-deploy-readiness/SKILL.md
spectracleanse-engineering/skills/spectracleanse-processing-pipeline/SKILL.md
spectracleanse-engineering/skills/spectracleanse-auth-billing/SKILL.md
spectracleanse-engineering/skills/spectracleanse-incident-response/SKILL.md
spectracleanse-engineering/skills/spectracleanse-documentation/SKILL.md
spectracleanse-engineering/skills/spectracleanse-testing-strategy/SKILL.md
spectracleanse-engineering/skills/spectracleanse-founder-operating-review/SKILL.md
Introduce SpectraCleanse-specific Claude agents for repo research and incident command.
  • Add a repo-researcher agent that systematically inspects files, cites evidence, and highlights discrepancies for any engineering question.
  • Add an incident-commander agent that structures production incidents by impact, hypotheses, containment, investigation, fix, and prevention.
spectracleanse-engineering/agents/spectracleanse-repo-researcher.md
spectracleanse-engineering/agents/spectracleanse-incident-commander.md
Create plugin-level metadata and changelog for the SpectraCleanse engineering plugin, including MCP template.
  • Add a README describing the plugin’s purpose, covered skills, stack facts, installation, agents, and safety notes.
  • Introduce a changelog documenting the initial plugin creation, registered skills/agents/docs, and known repo facts.
  • Add an example MCP configuration file with placeholder servers and strict guidance not to commit real tokens.
  • Register the plugin manifest describing skills, agents, and docs for Claude (content not shown in diff).
spectracleanse-engineering/README.md
spectracleanse-engineering/CHANGELOG.md
spectracleanse-engineering/.mcp.json.example
spectracleanse-engineering/.claude-plugin/plugin.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link
Copy Markdown

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@ChrisAdamsdevelopment ChrisAdamsdevelopment merged commit dc7445e into main May 24, 2026
6 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant